|
General
|
|
'Module ID'
|
Displays the module number to which the trunk belongs.
|
|
'Trunk ID'
|
Displays the selected trunk ID number.
|
|
'Trunk Configuration State'
|
Displays the status of the trunk:
|
■
|
"Not Configured": The trunk is not configured. |
|
■
|
"Active": The trunk is configured and currently active. |
|
■
|
"Inactive": The trunk is configured and currently is stopped (inactive). |
|
|
'Protocol Type'
configure voip > interface bri > protocol
[ProtocolType]
|
Defines the PSTN protocol for the trunk.
|
■
|
[50] BRI EURO ISDN = Euro ISDN over BRI
|
|
■
|
[54] BRI QSIG = QSIG over BRI
|
|
■
|
[55] BRI VN6 = VN6 over BRI
|
|
■
|
[56] BRI NTT = BRI ISDN Japan (Nippon Telegraph)
|
Note:
|
■
|
If you are modifying the parameter for an existing (configured) trunk through the Web interface, you must first stop the trunk. |
|
■
|
The ISDN BRI North American variants (NI-2, DMS-100, and 5ESS) are partially supported by the device. Please contact the sales representative of your purchased device before implementing this protocol.
|
|
|
Configuration
|
|
'Auto Clock Trunk Priority'
configure voip > interface bri > clock-priority clock-priority
[AutoClockTrunkPriority]
|
Defines the trunk priority for auto-clock fallback (per trunk parameter).
The valid range is 0 to 100, where 0 (default) is the highest priority and 100 indicates that the device does not perform a fallback to the trunk (typically, used to mark untrusted source of clock).
Note:
|
■
|
If you are modifying the parameter for an existing (configured) trunk through the Web interface, you must first stop the trunk. |
|
■
|
Fallback is enabled when the TDMBusPSTNAutoClockEnable parameter is set to 1. |
|
|
'Trace Level'
configure voip > interface bri > trace-level
[TraceLevel]
|
Defines the trace level:
|
■
|
[3] Only ISDN Q.931 Messages Trace |
|
■
|
[4] Layer 3 ISDN No Duplication Trace |
|
|
ISDN
BRI Configuration
|
|
'ISDN Termination Side'
configure voip > interface bri > isdn-termination-side
[TerminationSide]
|
Defines the ISDN termination side.
|
■
|
[0] User side = (Default) ISDN User Termination Equipment (TE) side. |
|
■
|
[1] Network side = ISDN Network Termination (NT) side. |
Note:
|
■
|
The device supports only Network side. |
|
■
|
For clock synchronization of E1/T1 interfaces, to configure if the clock is recovered (from the line) or generated (by the device), see the 'Clock Master' parameter (above). |
|
■
|
For clock synchronization of BRI interfaces: |
|
✔
|
If the parameter is configured to Network side, the clock is generated by the device. |
|
✔
|
If the parameter is configured to User side, the clock is recovered from the line. |
|
■
|
If you are modifying the parameter for an existing (configured) trunk through the Web interface, you must first stop the trunk.
|
|
|
'BRI Layer2 Mode'
configure voip > interface bri > isdn-layer2-mode
[BriLayer2Mode]
|
Defines Point-to-Point (P2P) or Point-to-Multipoint (P2MP) mode for BRI ports.
|
■
|
[0] Point to Point (default)
|
|
■
|
[1] Point to Multipoint |
Note: The parameter is applicable only to BRI interfaces and in Network Termination mode.
|
|
'Q.931 Layer Response Behavior'
configure voip > interface bri > isdn-bits-ns-behavior
[ISDNIBehavior]
|
Defines (by bit-field) several behavior options that influence the behavior of the Q.931 protocol.
|
■
|
[0] = Disable (default). |
|
■
|
[1] NO STATUS ON UNKNOWN IE = Q.931 Status message isn't sent if Q.931 received message contains an unknown/unrecognized IE. By default, the Status message is sent.
Note: This value is applicable only to ISDN variants in which sending of Status message is optional. |
|
■
|
[2] NO STATUS ON INV OP IE = Q.931 Status message isn't sent if an optional IE with invalid content is received. By default, the Status message is sent.
Note: This option is applicable only to ISDN variants in which sending of Status message is optional. |
|
■
|
[4] ACCEPT UNKNOWN FAC IE = Accepts unknown/unrecognized Facility IE. Otherwise, the Q.931 message that contains the unknown Facility IE is rejected (default).
Note: This option is applicable only to ISDN variants where a complete ASN1 decoding is performed on Facility IE. |
|
■
|
[128] SEND USER CONNECT ACK = The Connect ACK message is sent in response to received Q.931 Connect; otherwise, the Connect ACK is not sent.
Note: This option is applicable only to Euro ISDN User side outgoing calls. |
|
■
|
[2048] ALWAYS EXPLICIT = Always set the Channel Identification IE to explicit Interface ID, even if the B-channel is on the same trunk as the D-channel.
Note: This value is applicable only to 4/5ESS, DMS and NI-2 variants. |
|
■
|
[32768] ACCEPT MU LAW =Mu-Law is also accepted in ETSI. |
|
■
|
[65536] EXPLICIT PRES SCREENING = The calling party number (octet 3a) is always present even when presentation and screening are at their default.
Note: This option is applicable only to ETSI, NI-2, and 5ESS. |
|
■
|
[131072] STATUS INCOMPATIBLE STATE = Clears the call on receipt of Q.931 Status with incompatible state. Otherwise, no action is taken (default). |
|
■
|
[262144] STATUS ERROR CAUSE = Clear call on receipt of Status according to cause value. |
|
■
|
[524288] ACCEPT A LAW =A-Law is also accepted in 5ESS. |
|
■
|
[2097152] RESTART INDICATION = Upon receipt of a Restart message, acEV_PSTN_RESTART_CONFIRM is generated. |
|
■
|
[4194304] FORCED RESTART = On data link (re)initialization, send RESTART (Class 7) if there is no call. |
|
■
|
[134217728] NS BRI DL ALWAYS UP (0x08000000) = By default, a BRI trunk configured as Network side requests to disconnect the D-channel when there are no active calls on the trunk.
If you select this option, such a request is ignored by a Network side trunk.
If the option is configured for a User side trunk, it accepts the disconnect request but attempts to re-establish D-channel synchronization immediately afterward. |
Note:
|
✔
|
After a device restart or trunk initialization (i.e., configuration is applied), it's possible that D-channel synchronization is only established upon the first incoming or outgoing call.
|
|
✔
|
If this option is configured for a User side trunk, it may cause the D-channel alarm to be raised and cleared periodically because the opposite Network side may try to disconnect the D-channel if there are no ongoing calls.
|
|
■
|
[67108864] NS ACCEPT ANY CAUSE = Accept any Q.850 Cause IE from ISDN.
Note: This option is applicable only to Euro ISDN. |
|
■
|
[536870912] QSI ACCEPT ALCATEL FAC = Alcatel coding for redirect number and display name is accepted by the device.
Note: This option is applicable only to QSIG (and relevant for specific Alcatel PBXs such as OXE). |
|
■
|
[1073741824] QSI ENCODE INTEGER = If this bit is set, INTEGER ASN.1 type is used in operator coding (compliant to new ECMA standards); otherwise, OBJECT IDENTIFIER ASN.1 type is used.
Note: This option is applicable only to QSIG. |
|
■
|
[2147483648] 5ESS National Mode For Bch Maintenance = Use the National mode of AT&T 5ESS for B-channel maintenance. |
Note:
|
■
|
If you are modifying the parameter for an existing (configured) trunk through the Web interface, you must first stop the trunk.
|
|
■
|
To configure the device to support several ISDNIBehavior features, enter a summation of the individual feature values. For example, to support both [512] and [2048] features, set the parameter ISDNIBehavior is set to 2560 (i.e., 512 + 2048). |
|
■
|
When configuring through the Web interface, to select the options click the arrow button and then for each required option select 1 to enable. |
|
■
|
For BRI terminal endpoint identifier (TEI) configuration, instead of using the ISDNIBehavior parameter, use the following parameters: BriTEIConfigP2P_x, BriTEIConfigP2MP_x, BriTEIAssignTrigger_x, and BriTEIRemoveTrigger_x.
|
|
|
'Outgoing Calls Behavior'
configure voip > interface bri
> isdn-bits-outgoing-calls-behavior
[ISDNOutCallsBehavior]
|
Defines (by bit-field) several options that influence the behavior of the ISDN Stack outgoing calls. To select options, click the arrow button, and then for each required option, select 1 to enable. The default is 0 (i.e., disable).
|
■
|
[2] USER SENDING COMPLETE =The default behavior of the device (when this bit is not set) is to automatically generate the Sending-Complete IE in the Setup message. This behavior is used when overlap dialing is not needed. When overlap dialing is needed, set this bit and the behavior is changed to suit the scenario, i.e., Sending-Complete IE is added when required in the Setup message for Enblock mode or in the last Digit with Overlap mode. |
|
■
|
[16] USE MU LAW = The device sends G.711-m-Law in outgoing voice calls. When disabled, the device sends G.711-A-Law in outgoing voice calls.
Note: This option is applicable only to the Korean variant. |
|
■
|
[128] DIAL WITH KEYPAD = The device uses the Keypad IE to store the called number digits instead of the CALLED_NB IE.
Note: This option is applicable only to the Korean variant (Korean network). This is useful for Korean switches that don't accept the CALLED_NB IE. |
|
■
|
[256] STORE CHAN ID IN SETUP = The device forces the sending of a Channel-Id IE in an outgoing Setup message even if it's not required by the standard (i.e., optional) and no Channel-Id has been specified in the establishment request. This is useful for improving required compatibility with switches.On BRI lines, the Channel-Id IE indicates ‘any channel’. |
|
■
|
[2048] = The device accepts any IA5 character in the called_nb and calling_nb strings and sends any IA5 character in the called_nb, and is not restricted to extended digits only (i.e., 0-9,*,#). |
|
■
|
[16384] DLCI REVERSED OPTION = Behavior bit used in the IUA interface groups to indicate that the reversed format of the DLCI field must be used. |
Note:
|
■
|
If you are modifying the parameter for an existing (configured) trunk through the Web interface, you must first stop the trunk.
|
|
■
|
When using the ini file to configure the device to support several ISDNOutCallsBehavior features, add the individual feature values. For example, to support both [2] and [16] features, set ISDNOutCallsBehavior = 18 (i.e., 2 + 16). |
|
|
'Incoming Calls Behavior'
configure voip > interface bri > isdn-bits-incoming-calls-behavior
[ISDNInCallsBehavior]
|
Defines (by bit-field) several options that influence how the ISDN Stack INCOMING calls behave.
|
■
|
[32] DATA CONN RS = The device automatically sends a Q.931 Connect (answer) message on incoming Tel calls (Q.931 Setup). |
|
■
|
[64] VOICE CONN RS = The device sends a Connect (answer) message on incoming Tel calls. |
|
■
|
[2048] CHAN ID IN FIRST RS = The device sends Channel ID in the first response to an incoming Q.931 Call Setup message. If not set, the Channel ID is sent only if the device requires changing the proposed Channel ID. |
|
■
|
[4096] USER SETUP ACK = (Default) The Setup Ack message is sent by the SIP Gateway application layer and not automatically by the PSTN stack. |
|
■
|
[8192] CHAN ID IN CALL PROC = The device sends Channel ID in a Q.931 Call Proceeding message. |
|
■
|
[65536] PROGR IND IN SETUP ACK = (Default) The device includes Progress Indicator (PI=8) in Setup Ack message if an empty called number is received in an incoming Setup message. This option is applicable to the overlap dialing mode. The device also plays a dial tone (for TimeForDialTone) until the next called number digits are received. |
|
■
|
[2147483648] USER SCREEN INDICATOR = When the device receives two Calling Number IE's in the Setup message, the device, by default, uses only one of the numbers according to the following: |
|
✔
|
Network provided, Network provided: first calling number is used |
|
✔
|
Network provided, User provided: first calling number is used |
|
✔
|
User provided, Network provided: second calling number is used |
|
✔
|
User provided, user provided: first calling number is used |
When this bit is configured, the device behaves as follows:
|
✔
|
Network provided, Network provided: first calling number is used |
|
✔
|
Network provided, User provided: second calling number is used |
|
✔
|
User provided, Network provided: first calling number is used |
|
✔
|
User provided, user provided: first calling number is used |
Note:
|
■
|
If you are modifying the parameter for an existing (configured) trunk through the Web interface, you must first stop the trunk.
|
|
■
|
In the Web interface, the parameter displays the summation of the enabled optional bit values, in hex format. For example, the default value is 0x11000 (69632 in decimal), which is the summation of the two bit options, USER SETUP ACK (0x01000 or 4096 in decimal) and PROGR IND IN SETUP ACK (0x10000 or 65536 in decimal) that are enabled by default (i.e., 4096 + 65536 = 69632). |
|
■
|
When using the ini file to configure the device to support several ISDNInCallsBehavior features, enter a summation of the individual feature values. For example, to support both [2048] and [65536] features, set ISDNInCallsBehavior = 67584 (i.e., 2048 + 65536). |
|
|
'General Call Control Behavior'
configure voip > interface bri > isdn-bits-cc-behavior
[ISDNGeneralCCBehavior]
|
Defines (by bit-field) several general CC behavior options. To select the options, click the arrow button, and then for each required option, select 1 to enable. The default is 0 (i.e., disable).
|
■
|
[2] = Data calls with interworking indication use 64 kbps B-channels (physical only). |
|
■
|
[8] REVERSE CHAN ALLOC ALGO = Channel ID allocation algorithm. |
|
■
|
[16] = The device clears down the call if it receives a NOTIFY message specifying 'User-Suspended'. A NOTIFY (User-Suspended) message is used by some networks (e.g., in Italy or Denmark) to indicate that the remote user has cleared the call, especially in the case of a long distance voice call. |
|
■
|
[256] START WITH B CHAN OOS = B-channels start in the Out-Of-Service state (OOS). |
|
■
|
[512] CHAN ALLOC LOWEST = CC allocates B-channels starting from the lowest available B-channel id. |
|
■
|
[1024] CHAN ALLOC HIGHEST = CC allocates B-channels starting from the highest available B-channel id. |
|
■
|
[4096] NO B CHANEL CONTROL = When this bit is set, B-channels allocation and control is left according to the application level. Call control doesn't control/allocate B-channels. The application provides the B-channel information within the appropriate ACU primitives. Call Control simply provides the received Channel-ID IE contents to the user, without checking its availability, validity or consistency with other calls in progress. This bit should be set when the B-channel can be changed in Q.931 Proceeding, Alerting, or Connect. |
|
■
|
[16384] CC_TRANSPARENT_UUI = The UUI-protocol implementation of CC is disabled allowing the application to freely send UUI elements in any primitive, regardless of the UUI-protocol requirements (UUI Implicit Service 1). This allows more flexible application control on the UUI. When this bit is not set (default behavior), CC implements the UUI-protocol as specified in the ETS 300-403 standards for Implicit Service 1. |
|
■
|
[65536] GTD5 TBCT = CC implements the VERIZON-GTD-5 Switch variant of the TBCT Supplementary Service, as specified in FSD 01-02-40AG Feature Specification Document from Verizon. Otherwise, TBCT is implemented as specified in GR-2865-CORE specification (default behavior). |
Note:
|
■
|
If you are modifying the parameter for an existing (configured) trunk through the Web interface, you must first stop the trunk.
|
|
■
|
When using the ini file to configure the device to support several ISDNGeneralCCBehavior features, add the individual feature values. For example, to support both [16] and [32] features, set ISDNGeneralCCBehavior = 48 (i.e., 16 + 32). |
|
|
'ISDN NS Behaviour 2'
configure voip > interface bri > isdn-bits-ns-extension-behavior
[ISDNNSBehaviour2]
|
Defines (by bit-field) several options that influence the behavior of the Q.931 protocol.
|
■
|
[8] NS BEHAVIOUR2 ANY UUI = Any User to User Information Element (UUIE) is accepted for any protocol discriminator. This is useful for interoperability with non-standard switches. |
|
■
|
[16] NS BEHAVIOUR2 DISPLAY = The Display IE is accepted even if it is not defined in the QSIG ISDN protocol standard. This is applicable only when configuration is QSI. |
|
■
|
[64] NS BEHAVIOUR2 FAC REJECT = When this bit is set, the device answers with a Facility IE message with the Reject component on receipt of Facility IE with unknown/invalid Invoke component. This bit is implemented in QSIG and ETSI variants. |
|
■
|
[256] RESTART CLASS 7 IN FORCE RESTART = When this bit is set, the device sends RESTART (Class 7) if there is no call, on data link (re)initialization. |
|
|
Advanced Settings
|
|
'PSTN Alert Timeout'
configure voip > interface bri > pstn-alrt-timeout
[TrunkPSTNAlertTimeout]
|
Defines the Alert Timeout (ISDN T301 timer) in seconds for outgoing calls to PSTN, per trunk. This timer is used between the time that an ISDN Setup message is sent to the Tel side (IP-to-Tel call establishment) and a Connect message is received. If Alerting is received, the timer is restarted.
The range is 1 to 600. The default is 180.
|
|
'Local ISDN Ringback Tone Source'
configure voip > interface bri > local-isdn-rbt-src
[LocalISDNRBSource]
|
Determines whether the ringback tone is played to the ISDN by the PBX/PSTN or by the device, per trunk.
|
■
|
[0] PBX = (Default) PBX/PSTN plays the ringback tone. |
|
■
|
[1] Gateway = The device plays the ringback tone. |
Note: The parameter is used together with the [PlayRBTone2Trunk] parameter.
|
|
'Set PI in Rx Disconnect Message'
configure voip > interface bri > pi-in-rx-disc-msg
[PIForDisconnectMsg]
|
Defines the device's behavior per trunk when a Disconnect message is received from the ISDN before a Connect message is received.
|
■
|
[-1] Not Configured = (Default) Sends a 183 SIP response according to the received progress indicator (PI) in the ISDN Disconnect message. If PI = 1 or 8, the device sends a 183 response, enabling the PSTN to play a voice announcement to the IP side. If there isn't a PI in the Disconnect message, the call is released. |
|
■
|
[0] No PI = Doesn't send a 183 response to IP. The call is released. |
|
■
|
[1] PI = 1 = Sends a 183 response to IP. |
|
■
|
[8] PI = 8 = Sends a 183 response to IP. |
|
|
'ISDN Transfer Capabilities'
configure voip > interface bri > isdn-xfer-cab
[ISDNTransferCapability]
|
Defines the IP-to-ISDN Transfer Capability of the Bearer Capability IE in ISDN Setup messages, per trunk (where the x in the ini file parameter name denotes the trunk number and where 0 is Trunk 1).
|
■
|
[0] Audio 3.1 (default) |
Note: If the parameter is not configured or set to -1, Audio 3.1 capability is used.
|
|
'Progress Indicator to ISDN'
configure voip > interface bri > pi-to-isdn
[ProgressIndicator2ISDN]
|
Defines the Progress Indicator (PI) in ISDN messages per trunk sent to the PSTN.
|
■
|
[-1] Not Configured = (Default) The PI in ISDN messages is set according to the [PlayRBTone2Tel] parameter. |
|
■
|
[0] No PI = PI is not sent to ISDN. |
|
■
|
[1] PI = 1 = The PI value is sent to PSTN in Q.931/Proceeding and Alerting messages. Typically, the PSTN/PBX cuts through the audio channel without playing local ringback tone, enabling the originating party to hear remote Call Progress Tones or network announcements. |
|
■
|
[2] PI = 2 = The PI value is sent to PSTN in Q.931/Proceeding and Alerting messages. The destination address is non-ISDN. |
|
■
|
[8] PI = 8 = The PI value is sent to PSTN in Q.931/Proceeding and Alerting messages. Typically, the PSTN/PBX cuts through the audio channel without playing local ringback tone, enabling the originating party to hear remote Call Progress Tones or network announcements. |
|
|
'Select Receiving of Overlap Receiving'
configure voip > interface bri > ovrlp-rcving-type
[ISDNRxOverlap]
|
Determines the receiving (Rx) type of ISDN overlap dialing for Tel-to-IP calls, per trunk.
|
■
|
[0] None = (Default) Disabled. |
|
■
|
[1] Local receiving = ISDN Overlap Dialing - the complete number is sent in the INVITE Request-URI user part. The device receives ISDN called number that is sent in the 'Overlap' mode. The ISDN Setup message is sent to IP only after the number (including the Sending Complete IE) is fully received (via Setup and/or subsequent Info Q.931 messages). In other words, the device waits until it has received all the ISDN signaling messages containing parts of the called number, and only then it sends a SIP INVITE with the entire called number in the Request-URI. |
|
■
|
[2] Through SIP = Interworking of ISDN Overlap Dialing to SIP according to RFC 3578. The device sends the first received digits from the ISDN Setup message to the IP side in the initial INVITE message. For each subsequently received ISDN Info Q.931 message, the device sends the collected digits to the IP side in re-INVITE messages. |
|
■
|
[3] Through SIP INFO = Interworking of ISDN Overlap Dialing to SIP according to RFC 3578. The device sends the first received digits from the ISDN Setup message to the IP side in the initial INVITE message. For each subsequently received ISDN Info Q.931 message, the device sends the collected digits to the IP side in INFO messages. |
Note:
|
■
|
When configured to Through SIP or Through SIP INFO, you can define the minimum number of overlap digits to collect before sending the first SIP message for routing the call, using the MinOverlapDigitsForRouting parameter. |
|
■
|
When configured to Through SIP or Through SIP INFO, even if SIP 4xx responses are received during this ISDN overlap receiving, the device does not release the call. |
|
■
|
The MaxDigits parameter can be used to limit the length of the collected number for ISDN overlap dialing (if Sending Complete is not received). |
|
■
|
If a digit map pattern is defined (using the DigitMapping or DialPlanIndex parameters), the device collects digits until a match is found (e.g., for closed numbering schemes) or until a timer expires (e.g., for open numbering schemes). If a match is found (or the timer expires), the digit collection process is terminated even if Sending Complete is not received. |
|
■
|
For enabling ISDN overlap dialing for IP-to-Tel calls, use the ISDNTxOverlap parameter. |
|
|
'B-Channel Negotiation'
configure voip > interface e1-t1 > b-channel-nego-for-trunk
[BChannelNegotiationForTrunk]
|
Determines the ISDN B-channel negotiation mode, per trunk.
|
■
|
[-1] Not Configured = (Default) Use per device configuration of the BChannelNegotiation parameter. |
Note: The option Any is applicable only if TerminationSide is set to 0 (i.e., User side).
|
|
'Digital Out-Of-Service Behavior'
configure voip > interface > dig-oos-behavior
[DigitalOOSBehaviorForTrunk_x]
|
Defines the method for setting digital trunks to out-of-service state. The parameter is defined per trunk. The parameter is applicable to the Busy Out feature (see the [EnableBusyOut] parameter) and the Lock/Unlock per Trunk Group feature performed in the Trunk Group Settings table of the Web interface.
|
■
|
[-1] Not Configured = (Default) Use the settings of the [DigitalOOSBehavior] parameter ("global" parameter that applies to all trunks).
|
|
✔
|
ISDN: Sends ISDN Service messages to indicate out-of-service or in-service state for ISDN variants that support Service messages. For ISDN variants that do not support Service messages, the device sends an Alarm Indication Signal (AIS) alarm.
|
|
■
|
[1] Service =
Sends ISDN Service messages indicating out-of-service or in-service state.
|
|
✔
|
Graceful out-of-service disabled: The device rejects new incoming calls and immediately takes all channels (idle and busy) out-of-service, by sending Service messages on the B-channels. The device disconnects busy channels before it sends out-of-service Service messages on them.
|
|
✔
|
Graceful out-of-service enabled: The device rejects new incoming calls. If at least one busy channel exists during the graceful period, the device immediately takes all idle channels out-of-service and sends out-of-service Service messages to the other B-channels as soon as they become idle. When graceful period ends, the device disconnects all non-idle channels and then sends out-of-service Service messages to them.
|
When connectivity is restored for the Busy Out feature or the Trunk Group is unlocked, the device brings all the trunks back into service by sending in-service Service messages to all their B-channels.
|
■
|
[2] D-Channel = (Applicable only to ISDN and fully configured trunks) Takes the D-channel down or brings it up.
|
|
✔
|
Graceful out-of-service disabled: The device rejects new incoming calls and immediately takes the D-channel down.
|
|
✔
|
Graceful out-of-service enabled: The device rejects new incoming calls. Only when all channels are idle (when graceful period ends or when all channels become idle before graceful period ends, whichever occurs first), does the device take the D-channel down.
|
When connectivity is restored for the Busy Out feature or the Trunk Group is unlocked, the device brings the D-channels up again.
Note: For partially configured trunks (only some channels configured), this option only rejects new calls for the trunk; the D-channel remains up.
|
■
|
[3] Alarm = Sends or clears a PSTN Alarm Indication Signal (AIS) alarm.
|
|
✔
|
Graceful out-of-service disabled: The device rejects new incoming calls and immediately sends an AIS alarm.
|
|
✔
|
Graceful out-of-service enabled: The device rejects new incoming calls and only when all channels are idle (when graceful period ends or when all channels become idle before graceful period ends, whichever occurs first), does the device send an alarm on the trunk.
|
When connectivity is restored for the Busy Out feature or the Trunk Group is unlocked, the device clears the alarm.
Note: For partially configured trunks (only some channels configured), this option only rejects new calls for the trunk; no alarm is sent.
Note:
|
■
|
The parameter is applicable only to digital interfaces.
|
|
■
|
When configuring out-of-service behavior per trunk (see [DigitalOOSBehaviorForTrunk_x]), you must stop the trunk (Stop Trunk button in the Trunk Settings page), configure the parameter, and then restart the trunk (Apply Trunk Settings button in the Trunk Settings page) for the settings to take effect.
|
|
■
|
To define out-of-service behavior for all trunks (globally), see the [DigitalOOSBehavior] parameter.
|
|
■
|
For a description of the Busy Out feature and for enabling the feature, see the [EnableBusyOut] parameter.
|
|
■
|
To configure the graceful out-of-service period, see the [GracefulBusyOutTimeout] parameter.
|
|
■
|
If the ISDN variant does not support the configured out-of-service option of the parameter, the device sets the parameter to Default [0].
|
|
■
|
The x in the ini file parameter name denotes the trunk number, where 0 is Trunk 1.
|
|
|
'Digital Out-Of-Service Behavior'
dig-oos-behavior
[DigitalOOSBehavior]
|
Defines the method for setting all digital trunks to out-of-service state. To configure the out-of-service method per trunk, see the [DigitalOOSBehaviorForTrunk_x] parameter.
|
■
|
[0] Default = (Default) For a detailed description, see option [0] of the [DigitalOOSBehaviorForTrunk_x] parameter (per trunk setting).
|
|
■
|
[1] Service = Sends an ISDN Service message indicating out-of-service state (or in-service). For a detailed description, see option [1] of the [DigitalOOSBehaviorForTrunk_x] parameter (per trunk setting).
|
|
■
|
[2] D-Channel = Takes the D-Channel down or brings it up. For a detailed description, see option [2] of the [DigitalOOSBehaviorForTrunk_x] parameter (per trunk setting).
|
|
■
|
[3] Alarm = Sends or clears a PSTN Alarm Indication Signal (AIS) alarm. For a detailed description, see option [3] of the [DigitalOOSBehaviorForTrunk_x] parameter (per trunk setting).
|
|
■
|
[4] Block = Blocks the trunk. For a detailed description, see option [4] of the [DigitalOOSBehaviorForTrunk_x] parameter (per trunk setting).
|
|
■
|
[5] Service and D-Channel = Sends ISDN Service messages to indicate out-of-service or in-service state and takes the D-channel down or brings it up. For a detailed description, see option [5] of the [DigitalOOSBehaviorForTrunk_x] parameter (per trunk setting).
|
Note:
|
■
|
The parameter is applicable only to digital interfaces.
|
|
■
|
When using the parameter to configure out-of-service behavior for all trunks, you must reset the device for the settings to take effect.
|
|
■
|
If the ISDN variant does not support the configured out-of-service option of the parameter, the device sets the parameter to Default [0].
|
|
|
'Remove Calling Name'
configure voip > interface bri > rmv-calling-name
[RemoveCallingNameForTrunk_x]
|
Enables the device to remove the Calling Name for SIP-to-ISDN calls, per trunk.
|
■
|
[-1] Use Global Parameter = (Default) Settings of the global parameter [RemoveCallingName] are used. |
|
■
|
[0] Disable = Does not remove Calling Name. |
|
■
|
[1] Enable = Remove Calling Name. |
|
|
'Play Ringback Tone to Trunk'
configure voip > interface bri > play-rbt-to-trk
[PlayRBTone2Trunk_x]
|
Determines the playing method of the ringback tone to the trunk side, per trunk.
|
■
|
[-1] Not configured = (Default) The settings of the PlayRBTone2Tel parameter is used.
|
|
■
|
[0] Don't Play = When the device is configured for ISDN
, it doesn't play a ringback tone. No Progress Indicator (PI) is sent to the ISDN unless the [ProgressIndicator2ISDN_x] parameter is configured differently.
|
When the device is configured for ISDN, it operates according to the LocalISDNRBSource parameter, as follows:
|
✔
|
If the device receives a SIP 180 Ringing response (with or without SDP) and the LocalISDNRBSource parameter is set to 1, it plays a ringback tone and sends an ISDN Alert with PI = 8 (unless the [ProgressIndicator2ISDN_x] parameter is configured differently).
|
|
✔
|
If the LocalISDNRBSource parameter is set to 0, the device doesn't play a ringback tone and an Alert message without PI is sent to the ISDN. In this case, the PBX / PSTN plays the ringback tone to the originating terminal. Note that the receipt of a 183 response does not cause the device to play a ringback tone; the device sends a Progress message (unless SIP183Behaviour is set to 1). If the SIP183Behaviour parameter is set to 1, the 183 response is handled the same way as a 180 Ringing response.
|
|
■
|
[2] Prefer IP = Plays according to 'Early Media'. If a SIP 180 response is received and the voice channel is already open (due to a previous 183 early media response or due to an SDP in the current 180 response), the device configured for ISDN
doesn't play the ringback tone; PI = 8 is sent in an ISDN Alert message (unless the [ProgressIndicator2ISDN_x] parameter is configured differently).
If a 180 response is received, but the 'early media' voice channel is not opened, the device configured for ISDN operates according to the LocalISDNRBSource parameter:
|
|
✔
|
If LocalISDNRBSource is set to 1, the device plays a ringback tone and sends an ISDN Alert with PI = 8 to the ISDN (unless the [ProgressIndicator2ISDN_x] parameter is configured differently).
|
|
✔
|
If LocalISDNRBSource is set to 0, the device doesn't play a ringback tone. No PI is sent in the ISDN Alert message (unless the [ProgressIndicator2ISDN_x] parameter is configured differently). In this case, the PBX / PSTN plays a ringback tone to the originating terminal. Note that the receipt of a 183 response results in an ISDN Progress message (unless SIP183Behaviour is set to 1). If SIP183Behaviour is set to 1 (183 is handled the same way as a 180 with SDP), the device sends an Alert message with PI = 8 without playing a ringback tone.
|
|
■
|
[3] Play Local Until Remote Media Arrive = Plays tone according to received media. The behaviour is similar to option [2]. If a SIP 180 response is received and the voice channel is already open (due to a previous 183 early media response or due to an SDP in the current 180 response), the device plays a local ringback tone if there are no prior received RTP packets. The device stops playing the local ringback tone as soon as it starts receiving RTP packets. At this stage, if the device receives additional 18x responses, it does not resume playing the local ringback tone. Note that for ISDN trunks, this option is applicable only if LocalISDNRBSource is set to 1.
|
|
|
'Call Rerouting Mode'
configure voip > interface bri > call-re-rte-mode
[CallReroutingMode]
|
Determines whether ISDN call rerouting (call forward) is performed by the PSTN instead of by the SIP side. This call forwarding is based on Call Deflection for Euro ISDN (ETS-300-207-1) and QSIG (ETSI TS 102 393).
|
■
|
[1] ISDN Rerouting Enabled = Enables ISDN call rerouting. When the device sends the INVITE message to the remote SIP entity and receives a SIP 302 response with a Contact header containing a URI host name that is the same as the device's IP address, the device sends a Facility message with a Call Rerouting invoke method to the ISDN and waits for the PSTN side to disconnect the call. |
Note: When the parameter is enabled, ensure that you configure in the IP-to-Tel Routing table (PSTNPrefix ini file parameter) a rule to route the redirected call (using the user part from the 302 Contact header) to the same Trunk Group from where the incoming Tel-to-IP call was received.
|
|
'ISDN Duplicate Q931 BuffMode'
[ISDNDuplicateQ931BuffMode]
|
Determines the activation/deactivation of delivering raw Q.931 messages.
|
■
|
[0] 0 = (Default) ISDN messages aren't duplicated. |
|
■
|
[128] 1 = All ISDN messages are duplicated. |
|
|
'Trunk Name'
config-voip > interface bri name
[DigitalPortInfo_x]
|
Defines a descriptive name for a trunk. This can be used to help you easily identify the trunk.
The valid value is a string of up to 40 characters. The following special characters can be used (without quotation marks):
By default, the value is undefined.
|
